SPEC-PWF-FLD · v0.1 14 June 2026 Owner: Platform team
Drill-down of the master workflow map (SPEC-PWF), in the Service operations group. This process is a view over the spec — its requirements live in the Field PRD, its events & services in the Field service, its entities in the Field ERD. It is the engineer's execution of the visit the Incident and Coverage processes schedule. Lanes, steps and events render from workflow/workflow-catalog.js — nothing is defined twice.
1Trigger, outcome & lanes
What starts this process, where it ends, who acts and on which surfaces.
RiverSync Co., Ltd. · BangkokSPEC-PWF-FLD · 1 of 4
2The flow
Top to bottom in sequence; lanes are the actors. Node shape follows the master conventions — pills start and end the process, grey nodes are backbone events, diamonds are decisions.
Field visit — swimlane. Each step traces to a requirement in the table overleaf.SPEC-PWF-FLD · flow
RiverSync Co., Ltd. · BangkokSPEC-PWF-FLD · 2 of 4
3Steps
Each row is one node on the swimlane: who acts, what happens, the domain event it emits, and the requirement or rule it traces to.
RiverSync Co., Ltd. · BangkokSPEC-PWF-FLD · 3 of 4
4Related documentation
Every id, event, service and entity this process touches — each linked to the document that owns it.
5Rules in play
The WF-rules that bind this workflow — the master holds the full set; the DM-rules (ERD) and SVC-rules (Domain) they extend stay with those documents.
6Revision history
Version
Date
Changes
0.1
14 Jun 2026
First draft — Field visit joins the Service operations group (SPEC-PWF v0.5), composing with Incident and Coverage; the engineer's on-site execution of the scheduled visit, offline-first to sign-off.
RiverSync Co., Ltd. · BangkokSPEC-PWF-FLD · 4 of 4
